Broadcast signal transmitting/receiving device and method

ABSTRACT

A broadcast signal transmitting method is disclosed. The broadcast signal transmitting method comprises the steps of: processing at least one component of a broadcast service on the basis of a delivery protocol; generating service layer signaling (SLS) information including information on the component; generating service list table (SLT) information including bootstrap information for acquiring the SLS information; and generating a signal frame including a physical layer pipe (PLP) by performing a physical layer processing on the at least one component, the SLS information and the SLT information.

This application is a continuation of U.S. patent application Ser. No.17/202,938 filed on Mar. 16, 2021, which is a continuation of U.S.patent application Ser. No. 16/462,823 filed on May 21, 2019, now U.S.Pat. No. 11,039,186, which is a National Stage filing of InternationalApplication No. PCT/KR2017/007217 filed on Jul. 6, 2017, which claimsthe benefit of U.S. Provisional Application No. 62/429,087 filed on Dec.2, 2016 and U.S. Provisional Application No. 62/435,084 filed on Dec.16, 2016, all of which are hereby incorporated by reference in theirentirety for all purposes as if fully set forth herein.

TECHNICAL FIELD

The present disclosure relates to a broadcast signal transmissionapparatus, a broadcast signal reception apparatus, a broadcast signaltransmission method, and a broadcast signal reception method.

BACKGROUND ART

The termination of analog broadcasting is a driving force behind thedevelopment of various technologies for transmitting and receivingdigital broadcast signals. Compared to an analog broadcast signal, adigital broadcast signal may carry a large amount of video/audio data,and various types of additional data.

DISCLOSURE Technical Problem

A digital broadcasting system may provide high definition (HD) images,multi-channel audio, and various additional services. For digitalbroadcasting, however, the transmission efficiency of a large amount ofdata, the robustness of a transmission/reception network, and networkflexibility considering a mobile reception device need to be improved.

Technical Solution

To achieve the above object, the present disclosure proposes a broadcastsignal transmission method and a broadcast signal transmissionapparatus.

According to an embodiment of the present disclosure, a method oftransmitting a broadcast signal includes processing at least onecomponent of a broadcast service based on a delivery protocol,generating service layer signaling (SLS) information includinginformation about the at least one component, the SLS informationincluding service-based transport session instance description (S-TSID)information including description information about a session deliveringthe at least one component of the broadcast service, generating servicelist table (SLT) information including bootstrap information foracquiring the SLS information, and generating a signal frame including aphysical layer pipe (PLP) by performing physical layer processing on theat least one component, the SLS information, and the SLT information. Ifcomponents of the broadcast service are transmitted in multiple radiofrequency (RF) channels, a set of the components corresponds to aservice portion including a part of the components of the service or aservice duplicate including all the components of the broadcast service,and the service portion corresponds to an essential portion enablingpresentation of the broadcast service without use of the other portions,or a non-essential portion.

In the method of transmitting a broadcast signal according to theembodiment of the present disclosure, if the service portion or theservice duplicate of the broadcast service is transmitted in multiplechannels, the physical layer processing comprises selectively performingchannel bonding by distributing one PLP including the service portion orthe service duplicate to a plurality of channels. The service portion orthe service duplicate is delivered in a single channel without channelbonding, or in the plurality of channels with channel bonding.

In the method of transmitting a broadcast signal according to theembodiment of the present disclosure, if the service portion or theservice duplicate is delivered without channel bonding, an SLT of thechannel delivering the service portion or the service duplicatedescribes the service portion or the service duplicate, and a PLP ofeach channel delivering the service portion or the service duplicateincludes S-TSID information for the service portion or the serviceduplicate.

In the method of transmitting a broadcast signal according to theembodiment of the present disclosure, if the service portion isdelivered with channel bonding, when the essential portion is deliveredin a non-bonded PLP, a plurality of pieces of SLT information associatedwith a non-bonded PLP and a bonded PLP which deliver any portions of thebroadcast service list the broadcast service, and only SLT informationfor the essential portion lists a broadcast stream identifier (BSID) ofa broadcast stream delivering another service portion.

In the method of transmitting a broadcast signal according to theembodiment of the present disclosure, if the service portion isdelivered with channel bonding, when the essential portion is deliveredin a bonded PLP, one piece of SLT information associated with the bondedPLP delivering the essential portion lists the broadcast service, andlists a BSID of a broadcast stream delivering another service portion.

In the method of transmitting a broadcast signal according to theembodiment of the present disclosure, if the service duplicate isdelivered with channel bonding, a plurality of pieces of SLT informationassociated with a non-bonded PLP and a bonded PLP which deliver theservice duplicate list the broadcast service, and each of the pluralityof pieces of SLT information for the service duplicate lists a BSID of abroadcast stream delivering another service duplicate.

In the method of transmitting a broadcast signal according to theembodiment of the present disclosure, if the components are delivered ina plurality of broadcast streams of multiple broadcast channels, andchannel bonding is applied to the components, the S-TSID informationdescribes information about a session and a channel for a componentdelivered in a broadcast stream other than a broadcast stream deliveringthe S-TSID information.

Further, according to an embodiment of the present disclosure, abroadcast signal transmission apparatus includes a communication unitconfigured to transmit a broadcast signal, a memory configured to storedata, and a processor configured to control the communication unit andthe memory. The broadcast signal transmission apparatus is configured toprocess at least one component of a broadcast service based on adelivery protocol, to generate SLS information including informationabout the at least one component, the SLS information including S-TSIDinformation including description information about a session deliveringthe at least one component of the broadcast service, to generate SLTinformation including bootstrap information for acquiring the SLSinformation, and to generate a signal frame including a PLP byperforming physical layer processing on the at least one component, theSLS information, and the SLT information. If components of the broadcastservice are transmitted in multiple radio frequency (RF) channels, a setof the components corresponds to a service portion including a part ofthe components of the service or a service duplicate including all thecomponents of the broadcast service, and the service portion correspondsto an essential portion enabling presentation of the broadcast servicewithout use of the other portions, or a non-essential portion.

Advantageous Effects

The present disclosure may provide various broadcast services byprocessing data according to service characteristics, and thuscontrolling the quality of service (QoS) of each service or servicecomponent.

The present disclosure may achieve transmission flexibility bytransmitting various broadcast services in the same radio frequency (RF)signal bandwidth.

The present disclosure may provide a method and apparatus fortransmitting and receiving a broadcast signal, which enable reception ofa digital broadcast signal without errors even by using a mobilereception device or in an indoor environment.

The present disclosure may effectively support a next-generationbroadcast service in an environment supporting next-generation hybridbroadcasting which uses a terrestrial broadcast network and theInternet.

The additional effects of the present disclosure will be described belowin conjunction with the construction of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating a protocol stack according to anembodiment of the present disclosure.

FIG. 2 is a diagram illustrating a service discovery procedure accordingto an embodiment of the present disclosure.

FIG. 3 is a diagram illustrating a low level signaling (LLS) table and aservice list table (SLT) according to an embodiment of the presentdisclosure.

FIG. 4 is a diagram illustrating a user service bundle description(USBD) and a service-based transport session instance description(S-TSID), which are delivered over real-time object delivery overunidirectional transport (ROUTE) according to an embodiment of thepresent disclosure.

FIG. 5 is a diagram illustrating a USBD delivered over MPEG mediatransport (MMT) according to an embodiment of the present disclosure.

FIG. 6 is a diagram illustrating a link layer operation according to anembodiment of the present disclosure.

FIG. 7 is a diagram illustrating a link mapping table (LMT) according toan embodiment of the present disclosure.

FIG. 8 is a diagram illustrating a configuration of a broadcast signaltransmission apparatus for a next-generation broadcast service accordingto an embodiment of the present disclosure.

FIG. 9 is a diagram illustrating SLT information according to anembodiment of the present disclosure.

FIGS. 10 and 11 are diagrams illustrating a method of configuring abroadcast signal according to an embodiment of the present disclosure.

FIGS. 12 and 13 are diagrams illustrating a method of configuring abroadcast signal according to an embodiment of the present disclosure.

FIGS. 14 and 15 are diagrams illustrating a method of configuring abroadcast signal according to an embodiment of the present disclosure.

FIGS. 16 and 17 are diagrams illustrating a method of configuring abroadcast signal according to an embodiment of the present disclosure.

FIGS. 18 and 19 are diagrams illustrating a method of configuring abroadcast signal according to an embodiment of the present disclosure.

FIG. 20 is a block diagram illustrating a configuration of a broadcastsignal transmission/reception apparatus according to an embodiment ofthe present disclosure.

FIG. 21 is a flowchart illustrating a broadcast signal transmissionmethod according to an embodiment of the present disclosure.

FIG. 22 is a flowchart illustrating a broadcast signal reception methodaccording to an embodiment of the present disclosure.

BEST MODE FOR CARRYING OUT THE INVENTION

Reference will not be made in detail to the preferred embodiments of thepresent disclosure, examples of which are illustrated in theaccompanying drawings. The following detailed description taken inconjunction with the accompanying drawings is intended to explain thepreferred embodiments of the present disclosure, rather than to show theonly embodiments in which the disclosure may be practiced. Specificdetails are set forth in the following detailed description in order toprovide a thorough understanding of the present disclosure. However, itis obvious to those skilled in the art that the present disclosure canbe practiced without these specific details.

Although most terms used in the present disclosure have been selectedfrom general ones widely used in the art, some terms have beenarbitrarily selected by the applicant, and their meanings are explainedin detail in the following description as needed. Therefore, the presentdisclosure should be understood with the intended meanings of the termsrather than their simple names or meanings.

The present disclosure provides an apparatus and method for transmittingand receiving a broadcast signal for a next-generation broadcastservice. According to an embodiment of the present disclosure, thenext-generation broadcast services may be any of a terrestrial broadcastservice, a mobile broadcast service, an ultra-high-definition television(UHDTV) service, and so on. According to an embodiment of the presentdisclosure, a broadcast signal for a next-generation broadcast servicemay be processed in multiple input multiple output (MIMO) or non-MIMO.According to an embodiment of the present disclosure, non-MIMO schemesmay include multiple input single output (MISO), single input singleoutput (SISO), and so on. The present disclosure proposes an optimizedphysical profile (or system) that minimizes receiver complexity, whileachieving performance required for a specific purpose.

FIG. 1 is a diagram illustrating a protocol stack according to anembodiment of the present disclosure.

A service may be delivered to a receiver through a plurality of layers.A transmitting side may first generate service data. In the transmittingside, a delivery layer may process the service data, for transmission,and a physical layer may encode the processed service data into abroadcast signal and transmit the broadcast signal over broadcast orbroadband.

The service data may be formatted based on the ISO base media fileformat (ISO BMFF). An ISO BMFF media file may be used as a delivery,media encapsulation, and/or synchronization format for both broadbandand broadcast delivery. Service data refers to all data related to aservice, which may include, in concept, service components of a linearservice, signaling information for the service components, non-real time(NRT) data, and other files.

The delivery layer will be described. The delivery layer may provideservice data transport functionality. Service data may be delivered overbroadcast and/or broadband.

There may be two methods of broadcast service delivery.

One of the methods may be to process service data into media processingunits (MPUs) based on MPEG media transport (MMT), and transmit the MPUsby the MMT protocol (MMTP). In this case, the service data delivered bythe MMTP may include service components of a linear service and/orservice signaling information for the service components.

The other method may be to process service data into dynamic adaptivestreaming over HTTP (DASH) segments, and transmit the DASH segments byreal time object delivery over unidirectional transport (ROUTE). In thiscase, service data delivered by the ROUTE protocol may include servicecomponents of a linear service, service signaling information for theservice components, and/or NRT data. That is, non-timed data such as NRTdata and files may be delivered via ROUTE.

Data processed in conformance to the MMTP or the ROUTE protocol may beprocessed into Internet protocol (IP) packets through a user datagramprotocol (UDP)/IP layer. In broadcast service delivery, a service listtable (SLT) may also be delivered over broadcast through the UDP/IPlayer. The SLT may be delivered in a low level signaling (LLS) table.The SLT and the LLS table will be described later.

IP packets may be processed into link layer packets in a link layer. Thelink layer may encapsulate various formats of data delivered from ahigher layer into link layer packets, and then deliver the packets to aphysical layer. The link layer will be described later.

In hybrid service delivery, at least one service element may bedelivered via the broadband path. In hybrid service delivery, the datadelivered over broadband may include service components in a DASHformat, service signaling information for the service components, and/orNRT data. These data may be processed through HTTP/TCP/IP and deliveredto the physical layer for broadband transmission through the link layerfor broadband transmission.

The physical layer may process the data received from the delivery layer(higher layer and/or link layer) and transmit the data over broadcast orbroadband. Details of the physical layer will be described later.

A service will be described. A service may be a collection of servicecomponents presented to a user in aggregate. The components may be ofmultiple media types. The service may be either continuous orintermittent. The service may be real time or non-real time, and areal-time service may include a sequence of TV programs.

The service may be of multiple types. First, the service may be a linearaudio/video or audio service having app-based enhancement. Secondly, theservice may be an app-based service, the reproduction/configuration ofwhich is controlled by a downloaded application. Thirdly, the servicemay be an electronic service guide (ESG) service that provides an ESG.Fourthly, the service may be an emergency alert (EA) service thatprovides EA information.

For broadcast deliver of a linear service without app-based enhancement,service components may be delivered by (1) one or more ROUTE sessions,or (2) one or more MMTP sessions.

For broadcast delivery of a linear service with app-based enhancement,service components may be delivered by (1) one or more ROUTE sessions,or (2) zero or more MMTP sessions. In this case, data used for app-basedenhancement may be delivered in the form of NRT data or other files viathe ROUTE sessions. In an embodiment of the present disclosure,simultaneous use of two protocols for linear service components(streaming media components) in the same service may not be allowed.

For broadcast delivery of an app-based service, service components maybe delivered by one or more ROUTE sessions. In this case, service dataused for the app-based service may be delivered in the form of NRT dataor other files via the ROUTE sessions.

Some service components, some NRT data, files, and so on of such aservice may be delivered over broadband (hybrid service delivery).

That is, in an embodiment of the present disclosure, linear servicecomponents of one service may be delivered by the MMT protocol. Inanother embodiment of the present disclosure, linear service componentsof one service may be delivered by the ROUTE protocol. In anotherembodiment of the present disclosure, linear service components and NRTdata (NRT service components) of one service may be delivered by theROUTE protocol. In another embodiment of the present disclosure, linearservice components of one service may be delivered by the MMT protocol,while NRT data (NRT service components) may be delivered by the ROUTEprotocol. In the foregoing embodiments, some service components or someNRT data of the service may be delivered over broadband. Data for theapp-based service and the app-based enhancement may be delivered in theform of NRT data over broadcast via the ROUTE protocol or overbroadband. NRT data may also be referred to as locally-cached data.

Each ROUTE session includes one or more LCT sessions which carry all ora part of the content components making up the service. In streamingservice delivery, an LCT session may carry an individual component of auser service such as an audio, video or closed caption stream. Streamingmedia is formatted as DASH segments.

Each MMTP session includes one or more MMTP packet flows which carry MMTsignaling messages or all or a part of the content components. An MMTPpacket flow may carry MMT signaling messages or components formattedinto as MPUs.

For delivery of an NRT user service or system metadata, an LCT sessioncarries file-based content items. These content files may includecontinuous (time-based) or discrete (non-time-based) media components ofthe NRT service, or metadata such as service signaling or ESG fragments.Delivery of system metadata such as service signaling or ESG fragmentsmay also be achieved through a signaling message mode of the MMTP.

A receiver may detect a broadcast signal in a specific frequency, whilea tuner tunes to frequencies. The receiver may extract an SLT, andtransmit the SLT to a processing module. An SLT parser may parse theSLT, acquire data, and store the data in a channel map. The receiver mayacquire bootstrap information of the SLT, and deliver the bootstrapinformation to a ROUTE or MMT client. The receiver may acquire servicelayer signaling (SLS) from the bootstrap information, and store the SLS.A user service bundle description (USBD) and so on may be acquired andparsed by a signaling parser.

FIG. 2 is a diagram illustrating a service discovery procedure accordingto an embodiment of the present disclosure.

A broadcast stream delivered in a broadcast signal frame of the physicallayer may carry low level signaling (LLS). LLS data may be carried inthe payload of an IP packet delivered to a well-known IP address/port.The LLS may include an SLT according to its type. The LLS data may beformatted in the form of an LLS table. The first byte of every UDP/IPpacket carrying LLS data may be the start of an LLS table. Unlike theillustrated embodiment, an IP stream that delivers the LLS data may bedelivered along with other service data in the same PLP.

The SLT enables the receiver to build a list of services by rapidchannel scan, and provides access information to locate service layersignaling (SLS). The SLT includes bootstrap information. The bootstrapinformation enables the receiver to discover the SLS for each service.When the SLS, that is, service signaling information is delivered overROUTE, the bootstrap information may include information about thedestination IP address and destination port of an LCT channel carryingthe SLS or a ROUTE session including the LCT channel. When the SLS isdelivered over MMT, the bootstrap information may include informationabout the destination IP address and destination port of an MMTP sessioncarrying the SLS.

In the illustrated embodiment, the SLS of service #1 described in theSLT may be delivered via ROUTE, and the SLT may include bootstrapinformation sIP1, dIP1, and dPort1 about a ROUTE session including anLCT channel carrying the SLS. The SLS of service #2 described in the SLTmay be delivered via MMT, and the SLT may include bootstrap informationsIP2, dIP2, and dPort2 about an MMTP session including an MMTP packetflow carrying the SLS.

The SLS is signaling information describing characteristics of theservice, and may provide information for acquiring the service andservice components of the service, and include receiver capabilityinformation required to make a meaningful presentation of the service.If SLS is defined on a per-service level, the receiver has only toacquire appropriate SLS for a desired service without parsing whole SLSdelivered in a broadcast stream.

When the SLS is delivered by the ROUTE protocol, the SLS may bedelivered on a dedicated LCT channel of a ROUTE session indicated by theSLT. In some embodiments, this LCT channel may be identified by tsi=0.In this case, the SLS may include a user service bundle description(USBD)/user service description (USD), a service-based transport sessioninstance description (S-TSID), and/or a media presentation description(MPD).

The USBD/USD is one of SLS fragments, and may serve as a signaling hubdescribing detailed description information of a service. The USBD mayinclude service identification information, device capabilityinformation, and so on. The USBD may include reference information (URIreferences) of other SLS fragments (S-TSID, MPD, etc.). That is, theUSBD/USD may reference the S-TSID and the MPD. In addition, the USBD mayfurther include metadata information that enables the receiver todetermine a transport mode (broadcast/broadband). A detailed descriptionof the USBD/USD will be given below.

The S-TSID, which is one of SLS fragments, may provide overall sessiondescription information for a transport session carrying servicecomponents of the service. The S-TSID may provide transport sessiondescription information for a ROUTE session carrying service componentsof the service and/or an LCT channel of the ROUTE session. The S-TSIDmay provide component acquisition information for service componentsassociated with one service. The S-TSID may provide mapping between DASHrepresentations found in the MPD and the tsi of the service component.R=The S-TSID may provide the component acquisition information in theform of a tsi and the identifier of the associated DASH representation,and may or may not include a PLP ID in some embodiments. The receivermay collect audio/video components of one service from the componentacquisition information, and buffer and decode DASH media segments. TheS-TSID may be referenced by the USBD as described above. A detaileddescription of the S-TSID will be given later.

The MPD, which is one of SLS fragments, may provide a description of theDASH media presentation of the service. The MPD may provide resourceidentifiers for media segments and provide context information about theidentified resources within the DASH media presentation. The MPD maydescribe a DASH representation (service component) delivered overbroadcast, and also an additional DASH representation delivered overbroadband (hybrid delivery). The MPD may be referenced by the USBD asdescribed above.

If the SLS is delivered by the MMT protocol, the SLS may be deliveredover a dedicated MMTP packet flow of an MMTP session indicated by theSLT. In some embodiments, packet_id of MMTP packets delivering the SLSmay have a value of 00. In this case, the SLS may include a USBD/USDand/or MMT package (MP) table.

The USBD, which is one of SLS fragments, may describe detaileddescription information of a service, as is done in ROUTE. This USBD mayalso include information about references (URI references) to other SLSfragments. The USBD of the MMT may reference an MP table for MMTsignaling. In some embodiments, the USBD of the MMT may also includeinformation about reference to the S-TSID and/or the MPD. Here, theS-TSID may be for NRT data delivered by the ROUTE protocol. This isbecause even when linear service components are delivered by the MMTprotocol, NRT data may be delivered by the ROUTE protocol. In hybridservice delivery, the MPD may be for service components delivered overbroadband. A detailed description of the USBD of the MMT will be givenlater.

The MP table, which is an MMT signaling message for MPU components, mayprovide overall session description information for an MMTP sessioncarrying service components of the service. In addition, the MP tablemay include a description of assets delivered in the MMTP session. TheMP table is streaming signaling information for MPU components, and mayprovide a list of assets corresponding to one service and locationinformation (component acquisition information) about these components.Specific contents of the MP table may be defined in the MMT or modified.An asset is a multimedia data entity which is associated with a uniqueID, and is used to build a multimedia presentation. The asset maycorrespond to a constituent service component of one service. Astreaming service component (MPU) corresponding to a desired service maybe accessed using the MP table. The MP table may be referenced by theUSBD as described above.

Other MMT signaling messages may be defined. Additional informationrelated to an MMTP session and a service may be described by such MMTsignaling messages.

A ROUTE session is identified by a source IP address, a destination IPaddress, and a destination port number. An LCT session is identified bya unique transport session identifier (TSI) within the scope of a parentROUTE session. An MMTP session is identified by a destination IP addressand a destination port number. An MMTP packet flow is identified by aunique packet_id within the scope of a parent MMTP session.

In ROUTE, an S-TSID, a USBD/USD, an MPD or an LCT session deliveringthem may be referred to as a service signaling channel. In MMTP, aUSBD/UD, MMT signaling messages, or a packet flow delivering them may bereferred to as a service signaling channel.

Unlike the illustrated embodiment, one ROUTE or MMTP session may bedelivered in a plurality of PLPs. That is, one service may be deliveredin one or more PLPs. Unlike the illustrated embodiment, in someembodiments, components constituting one service may be delivered viadifferent ROUTE sessions. In addition, in some embodiments, componentsconstituting one service may be delivered via different MMTP sessions.In some embodiments, components constituting one service may bedelivered separately in a ROUTE session and an MMTP session. While notshown, components constituting one service may be delivered overbroadband (hybrid delivery).

FIG. 3 is a diagram illustrating an LLS table and an SLT according to anembodiment of the present disclosure.

An embodiment t3010 of the illustrated LLS table may include informationbased on an LLS_table_id field, a provider_id field, anLLS_table_version field, and/or an LLS_table_id field.

The LLS_table_id field may identify the type of the LLS table, and theprovider_id field may identify a service provider associated withservices signaled by the LLS table. The service provider is abroadcaster using all or a part of corresponding broadcast streams, andthe provider_id field may identify one of a plurality of broadcasterswhich are using the broadcast streams. The LLS_table_version field mayprovide information about the version of the LLS table.

According to the value of the LLS_table_id field, the LLS table mayinclude one of the above-described SLT, a rating region table (RRT)including information about a content advisory rating, SystemTimeinformation that provides information related to a system time, a commonalert protocol (CAP) message that provides information related toemergency alert. In some embodiments, other information may be includedin the LLS table.

An embodiment t3020 of the illustrated SLT may include an @bsidattribute, an @sltCapabilities attribute, an sltInetUrl element, and/ora Service element. Each field may be omitted or a plurality of fieldsmay be present, according to the value of the illustrated column, Use.

The @bsid attribute may be the identifier of a broadcast stream. The@sltCapabilities attribute may provide capability information requiredfor decoding and meaningfully presenting all services described in theSLT. The sltInetUrl element may provide base URL information used toacquire an ESG and service signaling information for the services of theSLT via broadband. The sltInetUrl element may further include an@urlType attribute which may indicate the type of data available withthe URL.

The Service element may include information about the services describedin the SLT, and the Service element may exist for each service. TheService element may include an @serviceId attribute, an @sltSvcSeqNumattribute, an @protected attribute, an @majorChannelNo attribute, an@minorChannelNo attribute, an @serviceCategory attribute, an@shortServiceName attribute, an @hidden attribute, an@broadbandAccessRequired attribute, an @svcCapabilities attribute, aBroadcastSvcSignaling element and/or an svcInetUrl element.

The @serviceId attribute is the identifier of the service, and the@sltSvcSeqNum attribute may indicate the sequence number of the SLTinformation of the service. The @protected attribute may indicatewhether at least one service component required for meaningfulpresentation of the service is protected. The @majorChannelNo attributeand the @minorChannelNo attribute may indicate the major channel numberand minor channel number of the service, respectively.

The @serviceCategory attribute may indicate the category of the service.The category of the service may be any of linear A/V service, linearaudio service, app-based service, ESG service, EAS service, and so on.The @shortServiceName attribute may provide a short name of the service.The @hidden attribute may indicate whether the service is intended fortesting or proprietary use. The @broadbandAccessRequired attribute mayindicate whether broadband access is required for meaningfulpresentation of the service. The @svcCapabilities attribute may providecapability information required for decoding and meaningfully presentingthe service.

The BroadcastSvcSignaling element may provide information related tobroadcast signaling of the service. This element may provide informationsuch as location, protocol, and address, for broadcasting signaling ofthe service, which will be described below in detail.

The svcInetUrl element may provide URL information for accessingsignaling information for the service via broadband. The sltInetUrlelement may further include an @urlType attribute which may indicate thetypes of data available with the URL.

The above-described BroadcastSvcSignaling element may include an@slsProtocol attribute, an @slsMajorProtocolVersion attribute, an@slsMinorProtocolVersion attribute, an @slsPlpId attribute, an@slsDestinationIpAddress attribute, an @slsDestinationUdpPort attribute,and/or an @slsSourcelpAddress attribute.

The @slsProtocol attribute may indicate the type (ROUTE, MMT, etc.) of adelivery protocol for SLS used by the service. The@slsMajorProtocolVersion attribute and the @slsMinorProtocolVersionattribute may indicate the major version number and minor version numberof the protocol used to deliver the SLS for the service, respectively.

The @slsPlpId attribute may provide a PLP identifier that identifies aPLP carrying the SLS of the service. In some embodiments, this field maybe omitted, and information about the PLP carrying the SLS may bechecked by using information in a later-described LMT and bootstrapinformation in the SLT in combination.

The @slsDestinationIpAddress attribute, the @slsDestinationUdpPortattribute, and the @slsSourceIpAddress attribute may indicate thedestination IP address, destination UDP port, and source IP address oftransport packets delivering the SLS of the service, respectively. Theseattributes may identify a transport session (ROUTE session or MMTPsession) delivering the SLS. These attributes may be included in thebootstrap information.

FIG. 4 is a diagram illustrating a USBD and an S-TSID delivered overROUTE according to an embodiment of the present disclosure.

An embodiment t4010 of the illustrated USBD may have a bundleDescriptionroot element. The bundleDescription root element may have auserServiceDescription element. The userServiceDescription element maybe an instance of a service.

The userServiceDescription element may include an @globalServiceIDattribute, an @serviceId attribute, an @serviceStatus attribute, an@fulIMPDUri attribute, an @sTSIDUri attribute, a name element, aserviceLanguage element, a capabilityCode element, and/or adeliveryMethod element. Each field may be omitted or a plurality offields may be present, according to the value of the illustrated column,Use.

The @globalServiceID attribute is a globally unique identifier of theservice, and may provide linkage to ESG data (Service@globalServiceID).The @serviceId attribute is a reference corresponding to the serviceentry of the SLT, and may be identical to service ID information of theSLT. The @serviceStatus attribute may indicate the status of theservice. This field may specify the status of the service as active orinactive.

The @fullMPDUri attribute may reference to an MPD fragment of theservice. The MPD may provide a presentation description of a servicecomponent delivered over broadcast network or broadband, as describedbefore. The @sTSIDUri attribute may reference to an S-TSID fragment ofthe service. The S-TSID may provide access-related parameters to atransport session carrying the service, as described above.

The name element may provide the name of the service. This element mayfurther include an @lang attribute indicating the language of the nameprovided by the name element. The serviceLanguage element may indicateavailable languages of the service. That is, this element may arrangethe languages in which the service may be provided.

The capabilityCode element may indicate capability or capability groupinformation for a receiver, required to meaningfully present theservice. This information is compatible with a capability informationformat provided in a service announcement.

The deliveryMethod element may provide transport-related informationpertaining to the content of the service accessed over broadcast orbroadband. The deliveryMethod element may include a broadcastAppServiceelement and/or a unicastAppService element. Each of these elements mayhave a basePattern element as a child element.

The broadcastAppService element may include transport-relatedinformation for DASH representations delivered over broadcast. The DASHrepresentations may include media components over the total period ofthe service media presentation.

The basePattern element of this element may indicate a character patternfor use by the receiver to match against a segment URL which is used fora DASH client to request media segments of the representation. Match mayimply delivery of the media segments over broadcast.

The unicastAppService element may include transport-related informationfor DASH representations delivered over broadband. The DASHrepresentations may include media components over the total period ofthe service media presentation.

The basePattern element of this element may indicate a character patternfor use by the receiver to match against the segment URL which may beused for a DASH client to request media segments of the representation.Match may imply delivery of the media segments over broadband.

An embodiment t4020 of the illustrated S-TSID may have an S-TSID rootelement. The S-TSID root element may include an @serviceId attributeand/or an RS element. Each field may be omitted or a plurality of fieldsmay be present, according to the value of the illustrated column Use.

The @serviceId attribute is the identifier of the service, and mayreference to the service of the USBD/USD. The RS element may describeinformation about ROUTE sessions in which the service components of theservice are carried. According to the number of ROUTE sessions, aplurality of RS elements may be present. The RS element may furtherinclude an @bsid attribute, an @sIpAddr attribute, an @dIpAddrattribute, an @dport attribute, an @PLPID attribute and/or an LSelement.

The @bsid attribute may be the identifier of a broadcast stream in whichthe service components of the service are delivered. If this field isomitted, a default broadcast stream may be a broadcast stream includinga PLP delivering the SLS of the service. The value of this field may beequal to that of the @bsid attribute of the SLT.

The @sIpAddr attribute, the @dIpAddr attribute, and the @dport attributemay indicate the source IP address, destination IP address, anddestination UDP port of the ROUTE session, respectively. When thesefields are omitted, default values may be the source address,destination IP address, and destination UDP port values of a currentROUTE session delivering the SLS, that is, the S-TSID. These fields maynot be omitted for any ROUTE session delivering the service componentsof the service, other than the current ROUTE session.

The @PLPID attribute may indicate PLP ID information about the ROUTEsession. If this field is omitted, a default value may be the PLP IDvalue of a current PLP delivering the S-TSID. In some embodiments, thisfield is omitted, and the PLP ID information about the ROUTE session maybe checked by using information of a later-described LMT and the IPaddress/UDP port information of the RS element in combination.

The LS element may describe information about LCT channels through whichthe service components of the service are delivered. According to thenumber of LCT channels, a plurality of LS elements may be present. TheLS element may include an @tsi attribute, an @PLPID attribute, an @bwattribute, an @startTime attribute, an @endTime attribute, a SrcFlowelement, and/or a RepairFlow element.

The @tsi attribute may represent the value of transport sessionidentifier (TSI) for the LCT channel. The LCT channel through which theservice components of the service are delivered may be identified by the@tsi attribute. The @PLPID attribute may indicate PLP ID information forthe LCT channel. In some embodiments, this field may be omitted. The @bwattribute may indicate the maximum bandwidth of the LCT channel. The@startTime attribute may indicate the start time of the LCT channel, andthe @endTime attribute may indicate the end time of the LCT channel.

The SrcFlow element may describe a ROURTE source flow. A ROUTE sourceprotocol is used to transmit a delivery object, and may establish atleast one source flow within one ROUTE session. The source flow maydeliver related objects as an object flow.

The RepairFlow element may describe a ROUTE repair flow. Deliveryobjects delivered according to the source protocol may be protectedaccording to forward error correction (FEC), and the repair protocol maydefine an FEC framework enabling the FEC protection.

FIG. 5 is a diagram illustrating a USBD delivered over MMT according toan embodiment of the present disclosure.

An embodiment of the illustrated USBD may have a bundleDescription rootelement. The bundleDescription root element may have auserServiceDescription element. The userServiceDescription element maybe an instance of one service.

The userServiceDescription element may include an @globalServiceIDattribute, an @serviceId attribute, a Name element, a serviceLanguageelement, a contentAdvisoryRating element, a Channel element, ampuComponent element, a routeComponent element, a broadbandComponentelement, and/or a ComponentInfo element. Each field may be omitted or aplurality of fields may be present, according to the value of theillustrated column, Use.

The @globalServiceID attribute, the @serviceId attribute, the Nameelement, and/or the serviceLanguage element may be identical tocorresponding fields of the USBD delivered over ROUTE. ThecontentAdvisoryRating element may represent the content advisory ratingof the service. This information is compatible with a content advisoryrating information format provided in a service announcement. TheChannel element may include information related to the service. Adetailed description of this element will be given later.

The mpuComponent element may provide a description of service componentsdelivered as MPUs of the service. This element may further include an@mmtPackageId attribute and/or an @nextMmtPackageId attribute. The@mmtPackageId attribute may reference to an MMT package of the servicecomponents delivered as the MPUs of the service. The @nextMmtPackageIdattribute may reference to an MMT package to be used after the MMTpackage referenced by the @mmtPackageId attribute in time. The MP tablemay be referenced through information of this element.

The routeComponent element may include a description of the servicecomponents of the service, delivered by ROUTE. Even when linear servicecomponents are delivered by the MMT protocol, NRT data may be deliveredaccording to the ROUTE protocol, as described before. The routeComponentelement may describe information about such NRT data. A detaileddescription of the routeComponent element will be given below.

The broadbandComponent element may include a description of the servicecomponents of the service, delivered over broadband. In hybrid servicedelivery, some service components of one service or other files may bedelivered over broadband. The broadbandComponent element may describeinformation about such data. The broadbandComponent element may furtherinclude an @fullMPDUri attribute. This attribute may reference to an MPDdescribing the service components delivered over broadband. In additionto hybrid service delivery, when the broadcast signal is weakened due todriving through a tunnel, this element may be required to supporthandoff between broadcast and broadband. When the broadcast signal isweak, the service components are acquired over broadband, and when thebroadcast signal becomes strong again, the service components areacquired over broadcast, thereby ensuring service continuity.

The ComponentInfo element may include information about the servicecomponents of the service. According to the number of the servicecomponents of the service, a plurality of ComponentInfo elements may bepresent. The ComponentInfo element may describe the type, role, name,identifier, or protection of each service component. Details of theComponentInfo element will be described later.

The afore-described Channel element may further include an @serviceGenreattribute, an @serviceIcon attribute, and/or a ServiceDescriptionelement. The @serviceGenre attribute may indicate the genre category ofthe service, and the @serviceIcon attribute may indicate a URL for anicon used to represent the service. The ServiceDescription element mayprovide a service description of the service, and further include an@serviceDescrText attribute and/or an @serviceDescrLang attribute. Theseattributes may indicate the text of the service description and thelanguage used in the text, respectively.

The afore-described routeComponent element may further include an@sTSIDUri attribute, an @sTSIDDestinationIpAddress attribute, an@sTSIDDestinationUdpPort attribute, an @sTSIDSourceIpAddress attribute,an @sTSIDMajorProtocolVersion attribute, and/or an@sTSIDMinorProtocolVersion attribute.

The @sTSIDUri attribute may reference to an S-TSID fragment. This fieldmay be identical to a corresponding field of the USBD delivered viaROUTE. The S-TSID may provide access-related information about theservice components delivered via ROUTE. The S-TSID may be present forNRT data delivered according to the ROUTE protocol in a situation inwhich linear service components are delivered by the MMT protocol.

The @sTSIDDestinationIpAddress attribute, the @sTSIDDestinationUdpPortattribute, and the @sTSIDSourceIpAddress attribute may indicate thedestination IP address, destination UDP port, and source IP address oftransport packets carrying the above-described S-TSID, respectively.That is, these fields may identify a transport session (MMTP session orROUTE session) carrying the above-described S-TSID.

The @sTSIDMajorProtocolVersion attribute and the@sTSIDMinorProtocolVersion attribute may indicate the major versionnumber and minor version number of a transport protocol used to deliverthe S-TSID, respectively.

The afore-described ComponentInfo element may further include an@componentType attribute, an @componentRole attribute, an@componentProtectedFlag attribute, an @componentId attribute, and/or an@componentName attribute.

The @componentType attribute may indicate the type of the component. Forexample, the @componentType attribute may indicate whether the componentis an audio, video or closed caption component. The @componentRoleattribute may indicate the role of the component. For example, if thecomponent is an audio component, the @componentRole attribute mayindicate whether the role is main audio, music, commentary, or the like.If the component is a video component, the @componentRole attribute mayindicate whether the role is primary video. If the component is a closedcaption component, the @componentRole attribute may indicate whether therole is a normal caption or an easy reader type.

The @componentProtectedFlag attribute may indicate whether the servicecomponent is protected, for example, encrypted. The @componentIdattribute may indicate the identifier of the service component. Thevalue of the @componentId attribute may be equal to that of the asset id(asset ID) of the MP table corresponding to this service component. The@componentName attribute may indicate the name of the service component.

FIG. 6 is a diagram illustrating a link layer operation according to anembodiment of the present disclosure.

The link layer may be the layer between the physical layer and thenetwork layer. The link layer may transmit data from the network layerto the physical layer at a transmitting side, and transmit data from thephysical layer to the network layer at a receiving side (t6010). Thepurpose of the link layer may be to abstract all input packet types intoa single format for processing by the physical layer, ensuringflexibility and future extensibility for as-yet-undefined input packettypes. In addition, the link layer may ensure transmission of input datain an efficient manner by providing options to compress redundantinformation in the headers of input packets. Operation of the link layerincluding overhead reduction, encapsulation, and so on are referred toas a link layer protocol, and packets generated by this protocol may bereferred to as link layer packets. The link layer may execute functionssuch as packet encapsulation, overhead reduction, and/or signalingtransmission.

At the transmitting, the link layer (ALP) may perform an overheadreduction procedure on input packets, and then encapsulate the inputpackets into link layer packets. In addition, in some embodiments, thelink layer may encapsulate input packets into link layer packets withoutperforming the overhead reduction procedure. The use of the link layerprotocol may lead to significant reduction of data transmission overheadin the physical layer, and the link layer protocol according to thepresent disclosure may provide IP overhead reduction and/or MPEG-2 TSoverhead reduction.

When the illustrated IP packets are input as input packets (t6010), thelink layer may sequentially perform IP header compression, adaptation,and/or encapsulation. In some embodiments, some processes may beomitted. First, an RoHC module may perform IP packet header compressionto thereby reduce unnecessary overhead. Context information may beextracted in the adaptation procedure, and transmitted out of band. TheIP header compression and adaption procedures may be collectivelyreferred to as IP header compression. Thereafter, the IP packets may beencapsulated into link layer packets in the encapsulation procedure.

When MPEG 2 TS packets are input as input packets, the link layer maysequentially perform the overhead reduction procedure and/or theencapsulation procedure on the TS packets. In some embodiments, someprocedure may be omitted. In overhead reduction, the link layer mayprovide sync byte removal, null packet deletion, and/or common headerremoval (compression). The sync byte removal may provide an overheadreduction of one byte per TS packet. Null packet deletion may beperformed in a manner that allows null packet reinsertion at thereceiving side. In addition, information common to consecutive headersmay be deleted (compressed) in a manner that allows recovery of theinformation at the receiving side. A part of each overhead reductionprocedure may be omitted. Thereafter, the TS packets may be encapsulatedinto link layer packets in the encapsulation procedure. The structure ofa link layer packet in which a TS packet is encapsulated may bedifferent from those of other types of packets.

First, IP header compression will be described.

Although an IP packet has a fixed header format, some informationrequired for a communication environment may be redundant in a broadcastenvironment. The link layer protocol may provide a mechanism forreducing broadcast overhead by compressing the header of the IP packet.

IP header compression may involve a header compressor/decompressorand/or an adaptation module. The IP header compressor (RoHC compressor)may reduce the size of the header of each IP packet based on a RoHCscheme. Subsequently, the adaptation module may extract contextinformation, and generate signaling information from each packet stream.A receiver may parse the signaling information related to the packetstream, and attach the context information to the packet stream. TheRoHC decompressor may reconstruct the original IP packet by recoveringthe packet header. Hereinbelow, IP header compression may refer only toIP header compression of a header compressor, or refer to both of IPheader compression and adaptation of an adaptation module, in concept.The same thing applies to decompression.

Now, adaptation will be described.

In the case of transmission via a unidirectional link, if the receiverhas no context information, the decompressor may not recover thereceived packet header until receiving full context data, therebycausing channel change delay and turn on delay. For this reason,configuration parameters and context information between the compressorand the decompressor may be transmitted out of band by the adaptationfunction. The adaptation function may construct link layer signaling byusing the context information and/or the configuration parameters. Theadaptation function may periodically transmit link layer signaling ineach physical frame by using the previous configuration parametersand/or context information.

Context information is extracted from compressed IP packets, and variousmethods may be used according to adaptation modes.

In Mode #1, no operation is performed on a compressed packet stream, andthe adaptation module may operate as a buffer.

In Mode #2, an IR packet may be detected from a compressed packetstream, and context information (static chain) is extracted. After theextraction, the IR packet may be converted into an IR-DYN packet. Theconverted IR-DYN packet may be transmitted in the packet stream in thesame order as the IR packet, replacing the original packet.

In Mode #3 (t6020), IR and IR-DYN packets are detected from a compressedpacket stream, and context information is extracted. A static chain anda dynamic chain may be extracted from the IR packet, and a dynamic chainmay be extracted from the IR-DYN packet. After the extraction, the IRand IR-DYN packets may be converted into general compressed packets. Theconverted packets may be transmitted in the packet stream in the sameorder as the IR and IR-DYN packets, replacing the original packets.

In each mode, after context information is extracted, the remainingpackets may be encapsulated and transmitted according to a link layerpacket structure for compressed IP packets. The context information maybe encapsulated and transmitted as link layer signaling according to alink layer packet structure for signaling information.

The extracted context information may be included in a RoHC-Udescription table (RDT), and transmitted separately from a RoHC packetflow. The context information may be transmitted along with othersignaling information through a specific physical data path. In someembodiments, the specific physical data path may be one of a generalPLP, a PLP carrying LLS, a dedicated PLP, or an L1 signaling path. TheRDT may be signaling information including context information (staticchain and/or dynamic chain) and/or information related to headercompression. In some embodiments, each time the context information ischanged, the RDT may be transmitted. Further, in some embodiments, theRDT may be transmitted in each physical frame. To transmit an RDT ineach physical frame, a previous RDT may be reused.

Before acquiring a packet stream, the receiver may acquire signalinginformation including an SLT, an RDT, an LMT, and so on by selecting aninitial PLP. When the receiver acquires the signaling information, thereceiver may acquire mappings among services, IP information, contextinformation, and PLPs by combining the signaling information. That is,the receiver may determine which service is transmitted in which IPstreams, and which PLP delivers which IP streams, and may also acquirecontext information about PLPs. The receiver may select a PLP carrying aspecific packet stream, and decode the PLP. The adaptation module mayparse the context information, and combine the context information withcompressed packets. In this manner, the packet stream may be recovered,and delivered to the RoHC decompressor. Decompression may then start.According to an adaptation mode, the receiver may detect IR packets, andstart decompression with a first received IR packet (Mode #1), detectIR-DYN packets and start decompression with a first received IR-DYNpacket (Mode #2), and start decompression with any general compressedpacket (Mode #3).

Packet encapsulation will be described below.

The link layer protocol may allow encapsulation of any type of inputpacket, including IP packets, TS packets, and so on into link layerpackets. Thus, the physical layer has only to process only one packetformat, independent of a network layer protocol type (herein, an MPEG-2TS packet is considered as a kind of network layer packet). Each networklayer packet or input packet is converted into the payload of a genericlink layer packet.

In the packet encapsulation procedure, segmentation may be used. If anetwork layer packet is too large to be processed in the physical layer,the network layer packet may be divided into two or more segments. Thelink layer packet header may include fields for segmentation at thetransmitting side and reassembly at the receiving side. Each segment maybe encapsulated into a link layer packet in the same order as itsoriginal position.

In the packet encapsulation procedure, concatenation may also be used.If a network layer packet is so small that the payload of a link layerpacket includes several network layer packets, concatenation may beperformed. The header of the link layer packet may include fields forconcatenation. In concatenation, each input packet may beencapsulated(concatenated?) into the payload of a link layer packet inthe same order as the original input order.

The link layer packet may include a header and payload. The header mayinclude a base header, an additional header, and/or an optional header.The additional header may be added according to a situation such asconcatenation or segmentation, and may include fields suitable for thesituation. In addition, the optional header may further be included todeliver additional information. Each header structure may be predefined.As described before, if input packets are TS packets, a link layerheader structure different from that of other packets may be used.

Link layer signaling will be described below.

Link layer signaling may operate below the IP layer. The receiving sidemay obtain link layer signaling earlier than IP level signaling such asLLS, an SLT, SLS, and so on. Accordingly, the link layer signaling maybe obtained before session establishment.

Link layer signaling may include internal link layer signaling andexternal link layer signaling. Internal link layer signaling may besignaling information generated in the link layer. The afore-describedRDT or the later-described LMT may be internal link layer signaling.External link layer signaling may be signaling information received froman external module, an external protocol, or a higher layer. The linklayer may encapsulate link layer signaling into a link layer packet, anddeliver the link layer packet. A link layer packet structure (headerstructure) for link layer signaling may be defined, and link layersignaling information may be encapsulated according to this structure.

FIG. 7 is a diagram illustrating an LMT according to an embodiment ofthe present disclosure.

The LMT may provide a list of higher-layer sessions carried in a PLP.The LMT may also provide additional information for processing linklayer packets carrying the higher-layer sessions. The higher-layersessions may be referred to as multicasts. Information about IP streamsand transport sessions carried in a specific PLP may be acquired fromthe LMT. In contrast, information about a PLP carrying a specifictransport session may be acquired from the LMT.

An LMT may be delivered in any PLP identified as carrying LLS. The PLPcarrying the LLS may be indicated by an LLS flag in L1 detail signalinginformation of the physical layer. The LLS flag may be a flag fieldindicating, for each PLP, whether LLS is delivered in the PLP. The L1detail signaling information may correspond to later-described PLS2data.

That is, the LMT may be delivered together with the LLS in the same PLP.Each LMT may describe mappings between PLPs and IP addresses/ports, asdescribed before. As described before, the LLS may include an SLT, andan IP address/port described by the LMT may be any IP address/portassociated with any service described in an SLT carried in an identifiedPLP carrying the LMT.

In some embodiments, PLP identifier information may be used in theabove-described SLT, SLS, and so on, so that information indicating aPLP carrying a specific transport session indicated by the SLT and SLSmay be checked.

In another embodiment, the PLP identifier information may be omitted inthe above-described SLT, SLS, and so on, and PLP information about thespecific transport session indicated by the SLT and SLS may be checkedby referring to information in the LMT. In this case, the receiver mayidentify an intended PLP by combining the LMT and other IP levelsignaling information. Even in this embodiment, PLP information mayremain in the SLT, SLS, and so on without being omitted.

The LMT according to the illustrated embodiment may include asignaling_type field, a PLP_ID field, a num_session field, and/orinformation about each session. Although the LMT of the illustratedembodiment describes IP streams transmitted in one PLP, a PLP loop maybe added to the LMT to describe information about a plurality of PLPs insome embodiments. In this case, as described before, the LMT maydescribe PLPs for any IP addresses/ports associated with any servicedescribed by the SLT delivered together with the LMT, as a PLP loop.

The signaling_type field may indicate the type of signaling informationdelivered in the table. For the LMT, the value of the signaling_typefield may be set to 0x01. The signaling_type field may be omitted. ThePLP_ID field may identify a PLP to be described. If a PLP loop is used,each PLP_ID field may identify a target PLP. The PLP_ID field and thesubsequent fields may be included in the PLP loop. The PLP_ID field asmentioned below identifies one PLP in the PLP loop, and the followingfields may be intended for the PLP.

The num_session field may indicate the number of higher layer sessionsdelivered in the PLP identified by the PLP_ID field. According to thenumber indicated by the num_session field, information about eachsession may be included. This information may include a src_IP_addfield, a dst_IP_add field, a src_UDP_port field, a dst_UDP_port field,an SID_flag field, a compressed_flag field, an SID field, and/or acontext_id field.

The src_IP_add field, the dst_IP_add field, the src_UDP_port field, andthe dst_UDP_port field may indicate the source IP address, destinationIP address, source UDP port, and destination UDP port of a transportsession among the higher layer sessions delivered in the PLP identifiedby the PLP_ID field.

The SID_flag field may indicate whether a link layer packet deliveringthe transport session has an SID field in its optional header. The linklayer packet delivering the higher layer session may have an SID fieldin the optional header, and the value of the SID field may be equal tothat of the SID field in the later-described LMT.

The compressed_flag field may indicate whether header compression isapplied to data of the link layer packet delivering the transportsession. In addition, the presence or absence of a later-describedcontext_id field may be determined according to the value of this field.If header compression is applied (compressed_flag=1), an RDT may exist,and the PLP ID field of the RDT may have a value equal to that of aPLP_ID field related to this compressed_flag field.

The SID field may indicate the SIDs (sub stream IDs) of link layerpackets delivering the transport session. The link layer packets mayinclude SIDs having values equal to that of this SID field in theiroptional headers. Thus, the receiver may filter the link layer packets,using information of the LMT and information about the SIDs of the linklayer packet headers, without the need for parsing all of the link layerpackets.

The context_id field may provide a reference for a context id (CID) inthe RDT. The CID information of the RDT may indicate the context ID of acorresponding compressed IP packet stream. The RDT may provide contextinformation about the compressed IP packet stream. The RDT and the LMTmay be associated by this field.

In the foregoing embodiments of signaling information/tables accordingto the present disclosure, the fields, elements, or attributes may beomitted or replaced with other fields. In some embodiments, otherfields, elements, or attributes may be added.

In an embodiment of the present disclosure, service components of oneservice may be delivered in a plurality of ROUTE sessions. In this case,SLS may be acquired from bootstrap information in an SLT. An S-TSID andan MPD may be referenced by the USBD of the SLS. The S-TSID may describenot only the ROUTE session delivering the SLS but also transport sessiondescription information of another ROUTE session carrying the servicecomponents. Thus, the service components delivered in the plurality ofROUTE sessions may all be collected. This is similarly applicable to thecase in which the service components of one service are delivered in aplurality of MMTP sessions. For reference, one service component may besimultaneously used by a plurality of services.

In another embodiment of the present disclosure, ESG bootstrapping maybe performed over broadcast or broadband. ULR information of an SLT maybe used by acquiring an ESG over broadband. ESG information may berequested to this URL.

In another embodiment of the present disclosure, one service componentof one service may be delivered over broadcast, and another servicecomponent may be delivered over broadband (hybrid). An S-TSID maydescribe components delivered over broadcast, thereby enabling a ROUTEclient to acquire desired service components. In addition, a USBD mayhave base pattern information, and thus describe which segments (whichcomponents) are delivered in which path. Accordingly, the receiver mayidentify a segment to be requested to a broadband server, and a segmentto be detected in a broadcast stream.

In another embodiment of the present disclosure, scalable coding of aservice may be performed. The USBD may have all capability informationrequired to render the service. For example, when one service isprovided in HD or UHD, the capability information of the USBD may have avalue of “HD or UHD”. The receiver may determine which component is tobe presented in order to render the UHD or HD service by using an MPD.

In another embodiment of the present disclosure, which SLS fragment isdelivered in LCT packets (USBD, S-TSID, MPD, etc.) may be identified bythe transport object indicator (TOI) fields of the LCT packets deliveredin an LCT channel delivering SLS.

In another embodiment of the present disclosure, app components to beused for app-based enhancement/an app-based service may be delivered asNRT components over broadcast, or may be delivered over broadband. Inaddition, app signaling for app-based enhancement may be performed by anapplication signaling table (AST) delivered along with the SLS. Inaddition, an event which is signaling for an operation to be performedby an app may be delivered in the form of an event message table (EMT)along with the SLS, may be signaled in an MPD, or may be in-bandsignaled in the form of a box within a DASH representation. The AST, theEMT, and so on may be delivered over broadband. App-based enhancementmay be provided by using the collected app components and the signalinginformation.

In another embodiment of the present disclosure, a CAP message may beincluded and provided in the above-described LLS table, for emergencyalert. Rich media content for emergency alert may also be provided. Richmedia may be signaled by a CAP message, and if rich media is present,the rich media may be provided as an EAS service signaled by the SLT.

In another embodiment of the present disclosure, linear servicecomponents may be delivered over broadcast according to the MMTprotocol. In this case, NRT data (e.g., app components) of the servicemay be delivered over broadcast according to the ROUTE protocol. Inaddition, data of the service may be delivered over broadband. Thereceiver may access an MMTP session delivering the SLS by using thebootstrap information of the SLT. The USBD of the SLS based on the MMTmay reference to the MP table to enable the receiver to acquire linearservice components formatted into MPUs delivered according to the MMTprotocol. In addition, the USBD may further reference to the S-TSID suchthat the receiver acquires NRT data delivered according to the ROUTEprotocol. In addition, the USBD may further reference to the MPD toprovide a reproduction description of data delivered over broadband.

In another embodiment of the present disclosure, the receiver maydeliver location URL information for acquiring a streaming componentand/or a file content item (file, etc.) to a companion device in amanner such as through a web socket. An application of a companiondevice may acquire components, data, and so on by a request to this URLthrough HTTP GET. In addition, the receiver may deliver information suchas system time information, emergency alert information, and so on tothe companion device.

FIG. 8 is a diagram illustrating a structure of a broadcast signaltransmission apparatus for a next-generation broadcast service accordingto an embodiment of the present disclosure.

The broadcast signal transmission apparatus for a next-generationbroadcast service according to an embodiment of the present disclosuremay include an input format block 1000, a bit interleaved coding &modulation (BICM) block 1010, a frame building block 1020, an orthogonalfrequency division multiplexing (OFDM) generation block 1030, and asignaling generation block 1040. An operation of each block of thebroadcast signal transmission apparatus will be described.

According to an embodiment of the present disclosure, for input data, anIP stream/packet and an MPEG2-TS may be main input formats, and otherstream types may be handled as general streams.

The input format block 1000 may demultiplex each input stream into oneor more data pipes to which independent codings and modulations areapplied. A data pipe is a basic unit for robustness control, and affectsquality of service (QoS). One or more services or service components maybe delivered in one data pipe. A data pipe is a logical channel in thephysical layer, which delivers service data or related metadata, fordelivering one or more services or service components.

Since QoS is dependent upon the characteristics of a service provided bythe broadcast signal transmission apparatus for a next-generationbroadcast service according to an embodiment of the present disclosure,data corresponding to each service needs to be processed in a differentmanner.

The BICM block 1010 may include a processing block for a profile (orsystem) to which MIMO is not applied and/or a processing block for aprofile (or system) to which MIMO is applied, and may include aplurality of processing blocks for processing the respective data pipes.

The processing block of the BICM block, to which MIMO is not applied,may include a data FEC encoder, a bit interleaver, a constellationmapper, a signal space diversity (SSD) encoding block, and a timeinterleaver. The processing block of the BICM block, to which MIMO isapplied, is different from the processing block of the BICM, to whichMIMO is not applied, in that the former further includes a cell worddemultiplexer and a MIMO encoding block.

The data FEC encoder may perform FEC encoding on an input BBF, usingexternal coding (BCH) and internal coding (LDPC), to generate a FECBLOCKprocedure. The external coding (BCH) is optional. The bit interleavermay interleave the output of the data FEC encoder to achieve optimizedperformance using a combination of an LDPC code and a modulation scheme.The constellation mapper may modulate a cell word from a bit interleaveror a cell word demultiplexer, in QPSK, QAM-16, irregular QAM (NUQ-64,NUQ-256, or NUQ-1024), or an irregular constellation (NUC-16, NUC-64,NUC-256, or NUC-1024), and provide a power-normalized constellationpoint. NUQ has an arbitrary shape, whereas QAM-16 and NUQ have a squareshape. Both of the NUQ and the NUC may be defined specially for eachcode rate and signaled by a parameter DP_MOD of PLS2 data. The timeinterleaver may operate at a data pipe level. A different timeinterleaving parameter may be configured for each data pipe.

The time interleaver according to the present disclosure may bepositioned between a BICM chain block and a frame builder. In this case,the time interleaver according to the present disclosure may use aselected one or both of a convolution interleaver (CI) and a blockinterleaver (BI) according to a PLP mode. A PLP according to anembodiment of the present disclosure is a physical path used in the sameconcept as the afore-mentioned DP, and its name may be changed accordingto a designer's intent. PLP modes according to an embodiment of thepresent disclosure may include a single PLP mode and a multiple PLP modeaccording to the number of PLPs processed by the broadcast signaltransmitter or the broadcast signal transmission apparatus. Timeinterleaving performed in different time interleaving schemes accordingto PLP modes may be referred to as hybrid time interleaving in thepresent disclosure.

A hybrid time interleaver may include a block interleaver (BI) and aconvolution interleaver (CI). If PLP_NUM=1, the BI is not applied (BIoff), and only the CI is applied. If PLP_NUM>1, both the BI and the CImay be applied (BI on). Different structures and operations of the CImay be applied when PLP_NUM>1 and when PLP_NUM=1. The hybrid timeinterleaver may perform an operation corresponding to a reverseoperation of the afore-mentioned hybrid time interleaver.

The cell word demultiplexer may be used to divide a single cell wordstream into dual cell word streams for MIMO processing. The MIMOencoding block may process the output of the cell word demultiplexer bya MIMO encoding scheme. The MIMO encoding scheme according to thepresent disclosure may be defined as full-rate spatial multiplexing(FR-SM) for providing a capacity increase with a relatively low increasein complexity at the receiving side. MIMO processing is applied at thedata pipe level. When a pair NUQ e_(1,i) and e_(2,i) output from theconstellation mapper is input to the MIMO encoder, a pair g1,i and g2,ioutput from the MIMO encoder may be transmitted in the same carrier kand OFDM symbol l of each transmission antenna.

The frame building block 1020 may map the data cells of the input datapipes to an OFDM symbol in one frame, and perform frequency interleavingfor frequency diversity.

According to an embodiment of the present disclosure, a frame is dividedinto a preamble, one or more frame signaling symbols (FSS), and a normaldata symbol. The preamble is a special symbol that provides a set ofbasic transmission parameters for effective transmission and receptionof a signal. The preamble may signal the basic transmission parametersand the transmission type of the frame. Particularly, the preamble mayindicate whether the emergency alert service (EAS) is provided in acurrent frame. The main purpose of the FSS is to transmit PLS data. Forfast synchronization, channel estimation, and fast decoding of PLS data,the FSS has a pipe pattern with a higher density than the normal datasymbol.

The frame building block may include a delay compensation block foradjusting a timing between a data pipe and corresponding PLS data toensure co-time between the data pipe and the PLS data at thetransmitting side, a cell mapper for mapping a PLS, a data pipe, anauxiliary stream, a dummy stream, and so on to an active carrier of anOFDM symbol in a frame, and a frequency interleaver.

The frequency interleaver may randomly interleave the data cellsreceived from the cell mapper to provide frequency diversity. Thefrequency interleaver may also operate for data corresponding to an OFDMsymbol pair including two successive OFDM symbols or data correspondingto one OFDM symbol, using different interleaving seed orders in order toachieve a maximum interleaving gain in a single frame.

The OFDM generation block 1030 may modulate an OFDM carrier by the cellsgenerated from the frame building block, insert a pilot, and generate atime signal for transmission. Further, the OFDM generation block 1030may sequentially insert guard intervals, and apply peak to average powerratio (PAPR) reduction processing, thereby generating a final RF signal.

The signaling generation block 1040 may generate physical layersignaling information for use in an operation of each functional block.The signaling information according to an embodiment of the presentdisclosure may include PLS data. The PLS provides means for enabling thereceiver to access a physical layer data pipe. The PLS data includesPLS1 data and PLS2 data.

The PLS1 data may be a first set of PLS data delivered in the FSS of aframe having a fixed size, coding, and modulation, which carries basicsystem information as well as a parameter required to decode the PLS2data. The PLS1 data provides basic transmission parameters including aparameter required to receive and decode the PLS2 data. The PLS2 data isa second set of PLP data transmitted in the FSS, for transmitting moredetailed PLS data of a data pipe and a system. PLS2 signaling mayfurther include two types of parameters: PLS2 static data (PLS2-STATdata) and PLS2 dynamic data (PLS2-DYN data). The PLS2 static data isPLS2 data that is static during the duration of a frame group, while thePLS2 dynamic data is PLS2 data that is dynamically changed in eachframe.

The PLS2 data may include FIC_FLAG information. A fast informationchannel (FIC) is a dedicated channel for transmitting cross-layerinformation that enables fast service acquisition and channel scan. TheFIC_FLAG information is a 1-bit field indicating whether an FIC is usedin a current frame group. When the value of the field is set to 1, anFIC is provided in the current frame. When the value of the field is setto 0, an FIC is not transmitted in the current frame. The BICM block1010 may include a BICM block for protecting PLS data. The BICM blockfor protecting PLS data may include a PLS FEC encoder, a bitinterleaver, and a constellation mapper.

The PLS FEC encoder may include a scrambler for scrambling PLS1 data andPLS2 data, a BCH encoding/zero insertion block for performing externalencoding on the scrambled PLS 1 and 2 data by a BCH code shortened forPLS protection, and inserting zero bits after the BCH encoding, an LDPCencoding block for performing encoding by an LDPC code, and an LDPCparity puncturing block. Only for the PLS1 data, zero-inserted outputbits may be permutated before the LDPC encoding. The bit interleaver mayinterleave each of the shortened and punctured PLS1 data and PLS2 data,and the constellation mapper may map the bit-interleaved PLS1 data andPLS2 data to a constellation.

A broadcast signal reception apparatus for a next-generation broadcastservice according to an embodiment of the present disclosure mayreversely perform the operation of the broadcast signal transmissionapparatus for a next-generation broadcast service, which has beendescribed with reference to FIG. 8 .

The broadcast signal reception apparatus for a next-generation broadcastservice according to an embodiment of the present disclosure may includea synchronization & demodulation module for performing demodulationcorresponding to a reverse operation of the procedure performed by thebroadcast signal transmission apparatus, a frame parsing module forparsing an input signal frame, and extracting data in which auser-selected service is transmitted, a demapping & decoding module forconverting an input signal into bit-domain data, deinterleaving thebit-domain data when needed, performing demapping corresponding tomapping applied for transmission efficiency, and correcting an errorthat has occurred to a transport channel by decoding, an outputprocessor for performing reverse operations of variouscompression/signal processing procedures performed by the broadcastsignal transmission apparatus, and a signaling decoding module foracquiring PLS information from the signal demodulated by thesynchronization & demodulation module, and processing the PLSinformation. The frame parsing module, the demapping & decoding module,and the output processor may perform the functions, using the PLS dataoutput from the signaling decoding module.

Now, a description will be given of the time interleaver. According toan embodiment of the present disclosure, a time interleaving group maybe mapped directly to one frame or spread across P_(I) frames. Further,each time interleaving group is divided into one or more (N_(TI)) timeinterleaving blocks. Each of the time interleaving blocks corresponds toone use of a time interleaver memory. The time interleaving blocks ofthe time interleaving group may include different numbers of XFECBLOCKs.In general, the time interleaver may also function as a buffer for datapipe data prior to the frame generation procedure.

According to an embodiment of the present disclosure, the timeinterleaver may be a twisted row-column block interleaver. The twistedrow-column block interleaver according to an embodiment of the presentdisclosure may write a first XFECBLOCK column-wise in a first column ofthe time interleaving memory, write a second XFECBLOCK in a next column,and write the remaining XFECBLOCKs of the time interleaving block in thesame manner. In the interleaving array, cells may be read out in adiagonal direction from a first row (to the right along the row,starting from a leftmost column) to a last row. In this case, to achievesingle memory deinterleaving at the receiving side irrespective of thenumber of XFECBLOCKs in the time interleaving block, the interleavingarray for the twisted row-column block interleaver may insert virtualXFECBLOCKs into the time interleaving memory. In this case, to achievethe single memory deinterleaving at the receiving side, the virtualXFECBLOCKs need to be inserted before other XFECBLOCKs.

A description will be given of methods of transmitting a service inmultiple RF channels. That is, methods of transmitting a service in twoor more RF channels, and methods of configuring signaling informationfor the same will be described.

A broadcast service may have components delivered in one or more RFchannels. A set of components of such a service within one RF channelmay be referred to as a portion of the service. When the set does notinclude all components of the service, this service set may be referredto as a portion. On the other hand, when a set of components of aservice includes all components of the service, and one or more suchsets of components are delivered, the set(s) may be referred to asduplicate(s) of the service. Each service represented by portions mayinclude an essential portion which is sufficient for a meaningfulprovisioning/presentation of the service without the use of the otherportions. Each service may include only one essential portion. Portionsother than the essential portion may be referred to as non-essentialportions. However, the use of the non-essential portions in addition tothe potential portion may provide a more appealing presentation of theservice.

A portion or duplicate of a service may be delivered on a single RFchannel without channel bonding. When channel bonding is applied to anALP packet stream, a portion or duplicate of a service may be deliveredin bonded RF channels. Hereinbelow, signaling methods for transmissionschemes with and without channel bonding will be described.

1. When service portions or duplicates are delivered without channelbonding.

(1) Each service represented by either service portions or duplicates isincluded in SLTs of RF channels in which the portions or duplicatesappear. Each of multiple listings of services as represented by itsportions or duplicates may have the same value of service ID, and thesame value of major/minor channel number. This enables the multipleportions or duplicates of a service carried in multiple RF channels tobe consolidated into a single service, when a receiver performs channelscan. An SLT entry for an essential portion or any duplicate of theservice may list the broadcast stream identifies (BSIDs) of broadcaststreams in which the other portions or duplicates may be found.

(2) An S-TSID may be delivered in a PLP of each RF channel that deliversa service portion or duplicate. The S-TSID for each portion or duplicateof the service may describe ROUTE sessions and LCT channels for eachcomponent of the service portion or duplicate.

2. When service portions are delivered with channel bonding, that is,when some service portions are delivered in bonded PLPs of a pluralityof RF channels,

2-1: If the essential portion of a service is delivered in a non-bondedchannel (PLP) of an RF channel,

(1) SLTs associated with both of a non-boded PLP and a bonded PLP thatdeliver any portions of the service list the service. Each of multiplelistings of the service as represented by a portion of the service mayhave the same value of service ID and the same value of major/minorchannel number. Only the SLT entry for the essential portion of theservice may list the BSIDs of broadcast streams in which the otherportions may be found.

(2)(a) An S-TSID may be delivered in a non-bonded PLP of each RF channelthat delivers a service portion. (b) An S-TSID may be delivered in abonded PLP of bonded RF channels that deliver another service portion.

In (a), each S-TSID instance may describe ROUTE sessions and LCTchannels for each component of the service portion delivered by thecorresponding non-bonded PLP(s) in the RF channel to which the PLPcarrying the S-TSID belongs. In (b), each S-TSID instance may describeROUTE sessions and LCT channels for each component of the serviceportion delivered by the corresponding PLP(s) in the bonded RF channelsto which the PLP carrying the S-TSID belongs.

2-2. If the essential portion of a service is delivered in bonded PLP(s)of bonded RF channels,

(1) Only a single SLT associated with the bonded PLP(s) that deliver theessential portion of the service may list the service. The SLT instanceof the service may list the BSIDS of broadcast streams in which theother service portions may be found.

(2) A single S-TSID for the service is delivered in a bonded PLP of thebonded RF channels that deliver the essential portion of the service.The S-TSID instance may describe ROUTE sessions and LCT channels for allthe components of the service.

3. When service duplicates are delivered with channel bonding, that is,when service duplicates are delivered in bonded PLP(s) of bonded RFchannels.

(1) SLTs associated with both of a non-bonded PLP and a bonded PLP thatdeliver duplicates of the service may list the service. Each of multiplelistings of the service as represented by its duplicates may have thesame value of service ID and the same value of major/minor channelnumber. An SLT entry for a duplicate of the service may list the BSIDSof broadcast streams in which the other duplicates may be found.

(2) (a) S-TSIDs may be delivered in a non-bonded PLP of each RF channelthat delivers a service duplicate. (b) Each S-TSID may be delivered in abonded PLP of bonded RF channels that deliver another service duplicate.

In (a), each S-TSID instance may describe ROUTE sessions and LCTchannels for each component of the service duplicate delivered by thecorresponding non-bonded PLP(s) in the RF channel to which the PLPcarrying the S-TSID belongs. In (b), each S-TSID instance may describeROUTE sessions and LCT channels for each component of the serviceduplicate delivered by the corresponding bonded PLP(s) in the bonded RFchannels to which the PLP carrying the S-TSID belongs.

Multiple tuners may be required to recover an ALP packet stream frombonded PLPs. For example, the same number of tuners as the number of RFchannels for the bonded PLPs may be required. To be able to acquire aservice to which channel bonding is applied, a single-tuner receivershould be able to acquire an SLT describing the service. If the S-TSIDof the service is acquired with a single tuner tuned to a particular RFchannel, then all components listed with the S-TSID may be acquired witha tuner tuned to the same RF channel. That is, with the above-describedsignaling structure, even a single-tuner receiver may identify allservices, and receive and acquire components of a service.

FIG. 9 illustrates SLT information according to an embodiment of thepresent disclosure.

FIG. 9 depicts another embodiment of the SLT illustrated in FIG. 3 , inwhich the SLT further includes signaling information for theafore-described multi-channel transmission. Therefore, the elements andattributes included in the SLT, described with reference to FIG. 3 willnot be described herein to avoid redundancy. The signaling informationadded to the SLT of FIG. 9 will be described below. All the addedsignaling information corresponds to subordinate information under theService element.

@essential: An @essential attribute 9010 in the Service elementindicates whether a service portion delivered in this broadcast streamis essential. When a service includes one or more portions delivered onone or more RF channels, the Boolean value of the @essential attributeindicates whether the essential portion of the service is delivered inthis broadcast stream. When at least one OtherBsid element with @typeset to 2 is present for the service, this Boolean attribute may bepresent. The default value of the @essential attribute may be set to“false”.

OtherBsid: An OtherBsid element 9020 corresponds to identifierinformation that identifies another broadcast stream delivering aduplicate or portion of this service. The format of an instance ofOtherBsid may be identical to the format of an instance of the @bsidattribute in the SLT. When the @essential attribute is not set to“true”, this element may not be present.

@type: A @type attribute 9030 indicates whether the broadcast streamidentified by the OtherBsid element includes a duplicate or a portion ofthis service. When the value of @type is set to 1, this may indicate aduplicate of the service, and when the value of @type is set to 2, thismay indicate a portion of the service. If the value of @type is set to2, this may indicate that the Service element represents a portion ofthe service. This service portion has components in the broadcast streamidentified by the identifier OtherBsid, and the service identifier ofthe service portion is given by the value of the @serviceId attribute ofthe parent Service element. When one or more OtherBsid elements arepresent under the parent Service element, the OtherBsid@type attributevalues of all these elements may be equal.

When the @type attribute is set to a value corresponding to “duplicate”,the @type attribute may indicate that the broadcast stream identified bythe OtherBsid element is a duplicate of the service. When the @typeattribute is set to a value corresponding to “portion”, the @typeattribute may indicate that the broadcast stream identified by theOtherBsid element is another portion including an additional componentof the service. When the @type attribute is set to the valuecorresponding to “portion”, the @type attribute may indicate that theService element represents a portion including a component in multiplebroadcast streams.

As described before, the S-TSID is an SLS metadata fragment thatcontains transport session description information for ROUTE sessionsand LCT channels within a media content component delivering a broadcastservice (ROUTE sessions and LCT channels in which media contentcomponents of a broadcast service are delivered). The S-TSID may includefile metadata for a delivery object or object flow carried in the LCTchannels of the service. The S-TSID may include additional informationabout payload formats and content components carried in the LCTchannels.

Components of a service may be delivered in a single broadcast stream orin multiple broadcast streams with(or without) channel bonding. TheS-TSID may describe only the ROUTE sessions and LCT channels for thebroadcast stream in which the S-TSID is delivered. However, if channelbonding is applied, and components of a service are delivered in one ormore broadcast streams, the S-TSID associated with the service maydescribe only the ROUTE sessions and LCT channels for other broadcaststreams than the broadcast stream in which the S-TSID is delivered.

For this purpose, the @bsid attribute may be included in the RS elementof the S-TSID. @bsid under the RS element may identify a broadcaststream carrying a content component of the broadcast service. If the RSelement does not include the @bsid attribute, a default broadcast streammay include a PLP carrying an SLS fragment for this service. The valueof this @bsid attribute may be equal to the value of @bsid in the SLT.

FIGS. 10 and 11 illustrate a method of configuring a broadcast signalaccording to an embodiment of the present disclosure.

FIG. 10 illustrates a signal frame of channel A in which an essentialportion is delivered in an embodiment in which portions of a service aredelivered in multiple RF channels without channel bonding.

In FIG. 10 , regarding the SLT included in PLP #0 of the signal frame ofchannel A, a Service element of the SLT associated with an essentialportion of a service has an OtherBsid element with @type set to 2. Inthe SLT of channel A (BSID=A), @essential for the service indicates thata service component delivered in channel A (BSID=A) is an essentialportion, and OtherBsid indicates channel B carrying another serviceportion.

The S-TSID included in PLP #1 of channel A delivering the S-TSIDdescribes LCT channels and ROUTE sessions for components delivered in abroadcast stream.

FIG. 11 illustrates a signal frame of channel B in which a non-essentialportion is delivered in an embodiment in which portions of a service aredelivered in multiple RF channels without channel bonding.

In FIG. 11 , regarding the SLT included in PLP #2 of the signal frame ofchannel B, a Service element of the SLT associated with an essentialportion of a service does not include an OtherBsid element. In the SLTof channel B (BSID=B), @essential for the service indicates that aservice component delivered in channel B (BSID=B) is not an essentialportion, and there is no OtherBsid. Preferably, the service is providedmainly with the essential portion, and including signaling for theessential portion in a non-essential portion may lead to waste ofsignaling resources.

The S-TSID included in PLP #3 of channel B delivering the S-TSIDdescribes LCT channels and ROUTE sessions for components delivered in abroadcast stream.

FIGS. 12 and 13 illustrate a method of configuring a broadcast signalaccording to an embodiment of the present disclosure.

FIG. 12 illustrates a signal frame of channel A carrying a serviceduplicate with channel number 9(1) in an embodiment in which duplicatesof a service are delivered in multiple RF channels without channelbonding.

In FIG. 12 , regarding the SLT included in PLP #0 of the signal frame ofchannel A, a Service element of the SLT associated with a duplicate of aservice has an OtherBsid element with @type set to 1. In the SLT ofchannel A (BSID=A), @essential for the service is omitted, and OtherBsidindicates channel B carrying another service duplicate.

The S-TSID included in PLP #1 of the signal frame of channel Adelivering the S-TSID describes LCT channels and ROUTE sessions forcomponents delivered in a broadcast stream.

FIG. 13 illustrates a signal frame of channel B in which a serviceduplicate with channel number 9(3) is delivered in an embodiment inwhich duplicates of a service are delivered in multiple RF channelswithout channel bonding.

In FIG. 13 , regarding the SLT included in PLP #2 of the signal frame ofchannel B, a Service element of the SLT associated with an essentialportion of a service includes an OtherBsid element with @type set to 1.In the SLT of channel B (BSID=B), @essential for the service is omitted,and OtherBsid indicates channel A carrying another service duplicate.

The S-TSID included in PLP #3 of the signal frame of channel Bdelivering the S-TSID describes LCT channels and ROUTE sessions forcomponents delivered in a broadcast stream.

FIGS. 14 and 15 illustrate a method of configuring a broadcast signalaccording to an embodiment of the present disclosure.

FIG. 14 illustrates a signal frame of channel A carrying an essentialportion in a non-bonded PLP in an embodiment in which portions of aservice are delivered in multiple RF channels with channel bonding.

In FIG. 14 , regarding the SLT included in PLP #0 of the signal frame ofchannel A, an SLT Service element associated with the essential portionof the service has an OtherBsid element with @type set to 2. In the SLTof channel A (BSID=A), @essential for the service is set to “true” andtwo OtherBsid elements indicate channel B and channel A B which deliverdifferent service portions, respectively.

The S-TSIDs included in PLP #1 and PLP #2 of the signal frame of channelA, which deliver the S-TSIDs, describe LCT channels and ROUTE sessionsfor components delivered in a broadcast stream.

The bonded PLP #2 in the signal frame of channel A includes an SLT. TheSLT included in the bonded PLP has @bsid set to A B, indicating twochannels. @essential is set to “false”. As described before, since onlyan SLT including an essential portion includes OtherBsid information,the SLT of PLP #2 does not include OtherBsid information.

FIG. 15 illustrates a signal frame of channel B carrying a non-essentialportion in a bonded PLP in an embodiment in which portions of a serviceare delivered in multiple RF channels with channel bonding. The signalframe of channel B delivers PLPs corresponding two services (service0x1001 and service 0x1004). Service 0x1004 may be a non-segmented fullservice.

In FIG. 15 , bonded PLP #2 of the signal frame of channel B and bondedPLP #2 of channel A are transmitted with channel bonding. The SLTincluded in PLP #4 of the signal frame of channel B includes Serviceelements for a plurality of services. The Service elements indicate thatservice 0x1001 is a non-essential portion, and service 0x1004 is anon-segmented full service.

The S-TSID included in PLP #3 of the signal frame of channel B, whichdelivers the S-TSID, describes LCT channels and ROUTE sessions forcomponents delivered in a broadcast stream.

FIGS. 16 and 17 illustrate a method of configuring a broadcast signalaccording to an embodiment of the present disclosure.

FIG. 16 illustrates a signal frame of channel A carrying an essentialportion in a bonded PLP in an embodiment in which portions of a serviceare delivered in multiple RF channels with channel bonding. The signalframe of channel A includes an SLT for non-bonded portions and an SLTfor bonded portions.

In FIG. 16 , regarding the SLT included in bonded PLP #2 of the signalframe of channel A, the SLT Service element associated with an essentialportion of the service has OtherBsid elements with @type set to 2. Inthe SLT of channel A (BSID=A), @essential for the service is set to“true” and two OtherBsid elements indicate channel B and channel B whichdeliver other service portions, respectively.

The S-TSIDs included in PLP #1 and PLP #2 of the signal frame of channelA, which deliver the S-TSIDs, describe LCT channels and ROUTE sessionsfor components delivered in a broadcast stream.

PLP #0 in the signal frame of channel A includes an SLT. The SLT of PLP#0 does not describe a service of a bonded PLP. Only an SLT associatedwith the essential portion of the service lists the service. The BSID ofthe SLT associated with the bonded PLP may indicate two channels “A B”.

FIG. 17 illustrates a signal frame of channel B carrying an essentialportion in a bonded PLP in an embodiment in which portions of a serviceare delivered in multiple RF channels with channel bonding. The signalframe of channel B delivers PLPs corresponding two services (service0x1001 and service 0x1004). Service 0x1004 may be a non-segmented fullservice.

In FIG. 17 , bonded PLP #2 of the signal frame of channel B and bondedPLP #2 of channel A are transmitted with channel bonding. The SLTincluded in PLP #4 of the signal frame of channel B includes a Serviceelement for a non-channel-bonded service.

FIGS. 18 and 19 illustrate a method of configuring a broadcast signalaccording to an embodiment of the present disclosure.

FIG. 18 illustrates a signal frame of channel A carrying a serviceduplicate in a bonded PLP in an embodiment in which duplicates of aservice are delivered in multiple RF channels with channel bonding. Thesignal frame of channel A includes an SLT for non-bonded portions and anSLT for bonded portions.

In FIG. 18 , regarding the SLT included in PLP #0 of the signal frame ofchannel A, the SLT Service element associated with a duplicate of theservice has an OtherBsid element with @type set to 1. In the SLT ofchannel A (BSID=A), there may not be @essential for the service. TwoOtherBsid elements indicate channel B and channel A B which deliverother service duplicates, respectively.

The S-TSIDs included in PLP #1 and PLP #2 of the signal frame of channelA, which deliver the S-TSIDs, describe LCT channels and ROUTE sessionsfor components delivered in a broadcast stream.

Bonded PLP #2 in the signal frame of channel A includes an SLT. The SLTincluded in the bonded PLP has @bsid set to A. In an embodiment, the SLTincluded in the bonded PLP may have @bsid set to A B, indicating twochannels. There may be no @essential attribute. Regarding the SLTincluded in bonded PLP #2 of the signal frame of channel A, the SLTService element associated with a duplicate of the service has OtherBsidelements with @type set to 1. In the SLT of bonded PLP #2, the twoOtherBsid elements indicate channel A and channel B which deliver otherservice duplicates, respectively.

FIG. 19 illustrates a signal frame of channel B carrying a serviceduplicate in a bonded PLP in an embodiment in which duplicates of aservice are delivered in multiple RF channels with channel bonding. Thesignal frame of channel B delivers PLPs carrying duplicates of theservice with different channel numbers.

In FIG. 19 , bonded PLP #2 of the signal frame of channel B and bondedPLP #2 of channel A are transmitted with channel bonding. The SLTincluded in PLP #4 of the signal frame of channel B includes a Serviceelement for a service. Further, the SLT of PLP #4 includes OtherBsidelements indicating broadcast streams carrying other duplicates of theservice. In the SLT of bonded PLP #4, the two OtherBsid elementsindicate channel A and channel A B which deliver other serviceduplicates, respectively.

FIG. 20 is a block diagram of a broadcast signal transmission/receptionapparatus according to an embodiment of the present disclosure.

In FIG. 20 , a broadcast signal transmission/reception apparatus 20000may include a communication unit 20010, a processor 20020, and a memory20030.

The communication unit 20010 may be connected to the processor 20020,and transmit/receive a broadcast signal. The communication unit 20010 ofthe broadcast signal transmission apparatus may upconvert data receivedfrom the processor 20020 to a transmission/reception band, and transmitthe upconverted signal. The communication unit 20010 of the broadcastsignal reception apparatus may downconvert received data and transmitthe downconverted data to the processor 20020. The communication unit20010 may receive an audio/video signal wiredly. The communication unit20010 may include at least one of a communication unit for wirelesscommunication and a communication unit for wired communication. Thecommunication unit 20010 may perform the physical layer processingdescribed before with reference to FIG. 8 . In an embodiment, thecommunication unit 20010 may perform the link layer processing describedbefore with reference to FIGS. 6 and 7 .

The processor 20020 may be connected to the communication unit 20010,and implement the broadcast signal processing technology of the ATSC 3.0system. The processor 20020 may be configured to perform the operationsaccording to various embodiments of the present disclosure, based on theafore-described drawings and the foregoing description. Further, amodule that implements the operations of the broadcast signaltransmission/reception apparatus 20000 according to various embodimentsof the present disclosure may be stored in the memory 20030, andexecuted by the processor 20020.

The memory 20030 is connected to the processor 20020, and stores varioustypes of information to operate the processor 20020. The memory 20030may reside inside or outside the processor 20020, and may be connectedto the processor 2002 by well-known means. The broadcast signaltransmission/reception apparatus 20000 may be implemented such that theforegoing various embodiments of the present disclosure are appliedindependently or two or more of them are applied at the same time.

Now, a description will be given of a broadcast signal transmissionmethod and a broadcast signal reception method in the broadcast signaltransmission/reception apparatus 20000. The broadcast signaltransmission apparatus may also be referred to as a broadcast signaltransmitter, and the broadcast signal reception apparatus may also bereferred to as a broadcast signal receiver.

FIG. 21 illustrates a broadcast signal transmission method according toan embodiment of the present disclosure.

Various embodiments of broadcast signal transmission described beforewith reference to FIGS. 1 to 20 are applicable to the broadcast signaltransmission method illustrated in FIG. 21 .

The broadcast signal transmitter may encode a component of a broadcastservice based on a delivery protocol (S21010). The delivery protocol mayinclude at least one of a ROUTE protocol or an MMT protocol.

The broadcast signal transmitter may generate SLS information for thebroadcast service component (S21020). The SLS information includesinformation for discovering and acquiring at least one component of thebroadcast service. The SLS information may include S-TSID informationincluding description information about a session that delivers at leastone component of the broadcast service.

The broadcast signal transmitter may generate SLT information for thebroadcast service (S21030). The SLT information includes bootstrapinformation for acquiring the SLS information.

The broadcast signal transmitter may perform physical layer processingon the component of the broadcast service, the SLS information, and theSLT information (S21040). The broadcast signal transmitter may generatea signal frame including a PLP by performing physical layer processingon higher-layer data.

If components of the broadcast service are transmitted in multiple RFchannels, a set of the components correspond to a service portionincluding some components of the service or a service duplicateincluding all components of the service. The service portion correspondsto a non-essential portion, or an essential portion with which theservice may be presented without the use of the other portions.

If service portions or service duplicates of the broadcast service aretransmitted in multiple channels, the physical layer processing mayinclude selectively performing channel bonding by distributing one PLPincluding a service portion or a service duplicate to a plurality ofchannels. The service portion or the service duplicate may be deliveredin a single channel without channel bonding or in the plurality ofchannels with channel bonding.

If the service portion or the service duplicate is delivered withoutchannel bonding, an SLT of a channel delivering the service portion orthe service duplicate may describe the service portion or the serviceduplicate, and a PLP of each channel delivering the service portion orthe service duplicate may include S-TSID information for the serviceportion or the service duplicate.

In the case where a service portion is delivered with channel boding, ifan essential portion is delivered in a non-bonded PLP, a plurality ofpieces of SLT information associated with a non-bonded PLP and a bondedPLP which deliver any portions of the service may list the service, andonly SLT information for the essential portion may list the broadcaststream ID (BSID) of a broadcast stream delivering another portion. Inthe case where a service portion is delivered with channel bonding, ifthe essential portion is delivered in a bonded PLP, one piece of SLTinformation associated with the bonded PLP delivering the essentialportion may list the service, and the SLT information may list the BSIDof a broadcast stream delivering another portion. In the case where aservice duplicate is delivered with channel bonding, a plurality ofpieces of SLT information associated with a non-bonded PLP and a bondedPLP that deliver duplicates of the service may list the service, andeach piece of SLT information for the service duplicates may list theBSID of a broadcast stream delivering another service duplicate.

In the case where service components are delivered in a plurality ofbroadcast streams of multiple broadcast channels, and channel bonding isapplied to the components, an S-TSID may describe information about asession and a channel for components delivered in a broadcast streamother than a broadcast stream delivering the S-TSID.

FIG. 22 illustrates a broadcast signal reception method according to anembodiment of the present disclosure.

Various embodiments of broadcast signal reception described before withreference to FIGS. 1 to 20 are applicable to the broadcast signalreception method illustrated in FIG. 22 .

The broadcast signal receiver may receive a broadcast signal (S22010).The broadcast signal receiver may receive a broadcast signal by tuningto a specific channel, and may receive a plurality of broadcast streamsby simultaneously tuning to a plurality of channels. In addition, thebroadcast signal receiver may perform physical layer processing on thereceived broadcast signal.

The broadcast signal receiver may parse SLT information included in thebroadcast signal (S22020). The SLT information includes bootstrapinformation for acquiring SLS information.

The broadcast signal receiver may acquire the SLS information based onthe SLT information (S22030). The SLS information includes informationfor discovering and acquiring at least one component of a broadcastservice.

The broadcast signal receiver may acquire a service component based onthe SLS information (S22040).

If components of the broadcast service are received in multiple RFchannels, a set of the components correspond to a service portionincluding some components of the service or a service duplicateincluding all components of the service. The service portion correspondsto a non-essential portion, or an essential portion with which theservice may be presented without the use of the other portions.

If service portions or service duplicates of the broadcast service arereceived in multiple channels, the physical layer processing may includeselectively performing channel bonding by distributing one PLP includinga service portion or a service duplicate to a plurality of channels. Theservice portion or the service duplicate may be delivered in a singlechannel without channel bonding or in the plurality of channels withchannel bonding.

If the service portion or the service duplicate is delivered withoutchannel bonding, an SLT of a channel delivering the service portion orthe service duplicate may describe the service portion or the serviceduplicate, and a PLP of each channel delivering the service portion orthe service duplicate may include S-TSID information for the serviceportion or the service duplicate.

In the case where a service portion is delivered with channel boding, ifthe essential portion is delivered in a non-bonded PLP, a plurality ofpieces of SLT information associated with a non-bonded PLP and a bondedPLP which deliver any portions of the service may list the service, andonly SLT information for the essential portion may list the broadcaststream ID (BSID) of a broadcast stream delivering another portion. Inthe case where a service portion is delivered with channel boding, ifthe essential portion is delivered in a bonded PLP, one piece of SLTinformation associated with the bonded PLP delivering the essentialportion may list the service, and the SLT information may list the BSIDof a broadcast stream delivering another portion. In the case where aservice duplicate is delivered with channel bonding, a plurality ofpieces of SLT information associated with a non-bonded PLP and a bondedPLP that deliver duplicates of the service may list the service, andeach piece of SLT information for the service duplicates may list theBSID of a broadcast stream delivering another service duplicate.

In the case where service components are delivered in a plurality ofbroadcast streams of multiple broadcast channels, and channel bonding isapplied to the components, an S-TSID may describe information about asession and a channel for a component delivered in a broadcast streamother than a broadcast stream delivering the S-TSID.

The present disclosure proposes a signaling method for transmitting andreceiving a service in multiple channels. The present disclosureproposes a method of signaling an additional service and a duplicate inone service, so that various services may be transmitted in multiplechannels. A receiver may acquire various portions/duplicatescorresponding to the service by using signaling information.

When channel bonding is applied to a broadcast signal, the receiverneeds signaling information related to the channel bonding. However, itis preferable to minimize unnecessary signaling information.Accordingly, when channel bonding is applied, a signal structure isdetermined based on what carries an essential portion in the presentdisclosure. In conclusion, the present disclosure may provide asignaling structure that optimizes a broadcast signal configurationaccording to multiple channel transmission and channel bonding.

Each step described in the foregoing embodiments may be performed byhardware/processors. Each module/block/unit described in the foregoingembodiments may operate in hardware/as a processor. Further, the methodsprovided by the present disclosure may be executed as code. The code maybe written to a processor-readable storage medium, and thus read by aprocessor of an apparatus.

While the drawings have been described separately for the convenience ofdescription, it is possible to implement a new embodiment by combiningthe embodiments illustrated in the drawings. The apparatuses and methodsaccording to the present disclosure are not intended to limit theconfigurations and methods of the foregoing embodiments. Rather, all ora part of the embodiments may be selectively combined so that manymodifications are made to the embodiments.

While preferred embodiments of the present disclosure have beendescribed above, the present disclosure is not limited to the specificembodiments. Those skilled in the art will appreciate that the presentdisclosure may be carried out in other specific ways than those setforth herein without departing from the spirit and essentialcharacteristics of the present disclosure. The above embodiments aretherefore to be construed in all aspects as illustrative and notrestrictive. The scope of the disclosure should be determined by theappended claims and their legal equivalents, not by the abovedescription, and all changes coming within the meaning and equivalencyrange of the appended claims are intended to be embraced therein.

Those skilled in the art will understand that many variations andmodifications can be made to the present disclosure. Therefore, thepresent disclosure is intended to embrace modifications and variationswithin the scope of the appended claims and their equivalents.

In the specification, both a device invention and a method invention arementioned, and their descriptions are applicable complementarily.

MODE FOR CARRYING OUT THE INVENTION

Various embodiments have been described in the best mode for carryingout the invention.

INDUSTRIAL APPLICABILITY

The present disclosure is used in the field of broadcast signaltransmission/reception.

It is obvious to those skilled in the art that many modifications andvariations may be made to the disclosure within the scope and spirit ofthe disclosure. Accordingly, it is to be understood that the disclosureis intended to embrace various modifications and variations fallingwithin the scope of the appended claims and their equivalents

The invention claimed is:
 1. A method of transmitting a broadcast signalby an apparatus, the method comprising: generating service layersignaling (SLS) information, the SLS information including service-basedtransport session instance description (S-TSID) information includingdescription information about a session delivering the at least onecomponent of a broadcast service; generating service list table (SLT)information including bootstrap information for acquiring the SLSinformation; transmitting, via a radio frequency (RF) channel, thebroadcast signal including the SLS information and the SLT information,wherein the SLT information includes a broadcast stream identifier(BSID) representing a first broadcast stream, wherein the SLTinformation further includes essential information representing whetheror not an essential portion of the broadcast service is transmitted, anOtherBSID representing a second broadcast stream, and type informationfor representing the second broadcast stream identified by the OtherBSIDdelivers a duplicate or a portion of the broadcast service that istransmitted via a RF channel, wherein a service ID for the portion orthe duplicate of the second broadcast stream has a same value of aservice ID for the broadcast service of the first broadcast stream. 2.An apparatus of transmitting a broadcast signal, the apparatuscomprising: a processor configured to generate service layer signaling(SLS) information, the SLS information including service-based transportsession instance description (S-TSID) information including descriptioninformation about a session delivering the at least one component of thebroadcast service, generate service list table (SLT) informationincluding bootstrap information for acquiring the SLS information; atransmitter configured to transmit, via a radio frequency (RF) channel,the broadcast signal including the SLS information and the SLTinformation, wherein the SLT information includes a broadcast streamidentifier (BSID) representing a first broadcast stream, wherein the SLTinformation further includes essential information representing whetheror not an essential portion of the broadcast service is transmitted, anOtherBSID representing a second broadcast stream, and type informationfor representing the second broadcast stream identified by the OtherBSIDdelivers a duplicate or a portion of the broadcast service that istransmitted via a RF channel, wherein a service ID for the portion orthe duplicate of the second broadcast stream has a same value of aservice ID for the broadcast service of the first broadcast stream.
 3. Amethod for receiving a broadcast signal by an apparatus, the methodcomprising: receiving, via a radio frequency (RF) channel, the broadcastsignal including service layer signaling (SLS) information, the SLSinformation including service-based transport session instancedescription (S-TSID) information including description information abouta session delivering the at least one component of a broadcast serviceand service list table (SLT) information including bootstrap informationfor acquiring the SLS information, wherein the SLT information includesa broadcast stream identifier (BSID) representing a first broadcaststream, wherein the SLT information further includes essentialinformation representing whether or not an essential portion of thebroadcast service is transmitted, an OtherBSID representing a secondbroadcast stream, and type information for representing the secondbroadcast stream identified by the OtherBSID delivers a duplicate or aportion of the broadcast service that is transmitted via the RF channel,wherein a service ID for the portion or the duplicate of the secondbroadcast stream has a same value of a service ID for the broadcastservice of the first broadcast stream; and decoding, by a decoder, thebroadcast signal.
 4. An apparatus for receiving a broadcast signal, theapparatus comprising: a hardware receiver configured to receive, via aradio frequency (RF) channel, a broadcast signal; and a processor todecode the broadcast signal including service layer signaling (SLS)information,the SLS information including servic-basedtransport sessioninstance description (S-TSID) information including descriptioninformation about a session delivering the at least one component of abroadcast service and service list table (SLT) information includingbootstrap information for acquiring the SLS information, wherein the SLTinformation includes a broadcast stream identifier (BSID) representing afirst broadcast stream, wherein the SLT information further includesessential information representing whether or not an essential portionof the broadcast service is transmitted, an OtherBSID representing asecond broadcast stream, and type information for representing thesecond broadcast stream identified by the OtherBSID delivers a duplicateor a portion of the broadcast service that is transmitted via the RFchannel, wherein a service ID for the portion or the duplicate of thesecond broadcast stream has a same value of a service ID for thebroadcast service of the first broadcast stream.